Skip to content

Add changelog-sync workflow#259

Draft
yonib05 wants to merge 4 commits into
strands-agents:mainfrom
yonib05:changelog-sync
Draft

Add changelog-sync workflow#259
yonib05 wants to merge 4 commits into
strands-agents:mainfrom
yonib05:changelog-sync

Conversation

@yonib05

@yonib05 yonib05 commented Jun 11, 2026

Copy link
Copy Markdown
Member

Description

Adds a changelog-sync.yml workflow that, on each published release, opens a cross-repo PR into strands-agents/harness-sdk to update the changelog page (which aggregates releases across the Strands SDKs and lives in harness-sdk).

It's a thin caller of the shared strands-agents/devtools/changelog-release-pr composite action (see the devtools PR) — all parsing/rendering logic lives there, deterministically, with no logic duplicated here. Also supports workflow_dispatch with a backfill input for the one-time historical import.

Related Issues

Part of the Strands changelog feature (harness-sdk site PR + devtools action PR).

Type of Change

New feature

Testing

  • Workflow YAML validated (parses cleanly).
  • The devtools action it calls is unit-tested (38 tests) and validated end-to-end against the harness-sdk changelog schema, including a real evals release (v0.2.1).

Notes for reviewers

  • Auth (secrets.CHANGELOG_PR_TOKEN) is a placeholder pending confirmation. The evals job's own github.token can't open a PR on harness-sdk; this needs a token with pull-requests:write + contents:write on harness-sdk. Please point me at the org's existing cross-repo automation token to reuse rather than provisioning a new secret.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant